Back to Main Menu

Upgrading myData between major versions (1.x ,1.3, 1.4, 1.5, 1.6)

Outcomes: Gain an understanding of how to upgrade myData from on older version to a newer version.

Note: Please contact Assetic support if you require installation files for versions of myData prior to 1.8.x.

This guide covers upgrading myData between major versions

Overarching Principles

Where a client wishes to preserve any of the following during upgrades, they should contact Assetic to perform the upgrade.

  • Archives (historical data)
  • Valuations history and data
  • SMP Strategic Maintenance Planning configuration, history and data
  • Integration (note this usually requires upgrading third party systems as well)

Prerequisites

The client needs to supply the following information

  1. SQL Server version the myData database is on i.e. SQL SERVER 2008R2 (this is the minimum for myData 1.6 and above)
  2. Current myData version including the minor numbers 1.3.23010
  3. Microsoft .NET Framework i.e. .Net Framework 4.0 (this is the minimum for myData 1.6 and above)
  4. User domain for licensing myData 1.6 and above. ( It can be found by opening command prompt and entering "echo %userdomain%" ) 

myData 1.0 to myData 1.3

This upgrade takes 1 to 2 Days depending on size and scope of client data. 

Task
Timing

Client supplies a zipped backup of the database

  1. myData is taken offline
  2. Client uploads myData database to Assetic's file server

1 Day

Close of business on the week prior to upgrade

Assetic upgrades client database to final 1.3 version of myData

  1. Upgrading 1.0 to 1.3
    1. Patching supplied 1.0 database to final 1.3 release
    2. Run the SMP upgrade utility

    3. Perform audit checks to ensure integrity has been maintained

      1. Asset Register
      2. Valuations
      3. SMP
 1-2 Days
Proceed to myData 1.3 to myData 1.4

If Web Services integration is being used, clients should contact Assetic before proceeding as third party systems will also need to be upgraded

Assetic returns upgraded database to client

  1. Backup and zip database
  2. Include links for
    1. Current myData release
    2. Upgraded database with licence applied
    3. Relevant deployment guides
 1 Day

Client restores myData database

  1. Install myData as per Software Install and Update
  2. Update SQL Server to 2008R2 or newer
  3. Create Live and Training environments (Recommended naming of myData databases)Create a new myData configuration file (Global Configuration File Example)
    1. Restore database to each environment


 1 Day
 

myData 1.3 to myData 1.4

This upgrade takes 1 to 2 Days depending on size and scope of client data.

If integration using web services is being used clients should contact Assetic before proceeding as third-party systems will also need to be upgraded

 

Task
Timing

Client supplies a zipped backup of the database

  1. myData is taken offline
  2. Client uploads myData database to Assetic's file server

1 Day

Close of business on the week prior to upgrade

Assetic upgrades client database to final 1.4 version of myData

  1. Upgrading 1.3
    1. Patching supplied 1.3 database to final 1.3 release
    2. Run the 1.4 archive upgrade utility

  2. Upgrading 1.4

    1. Run the 1.4 admin utility

    2. Perform audit checks to ensure integrity has been maintained

      1. Asset Register
      2. Valuations
      3. SMP
 1-2 Days

Proceed to myData 1.4 to myData 1.5

If Web Services integration is being used, clients should contact Assetic before proceeding as third party systems will also need to be upgraded

Assetic returns upgraded database to client

  1. Backup and zip database
  2. Include links for
    1. Current myData release
    2. Upgraded database with licence applied
    3. Relevant deployment guides
 1 Day

Client restores myData database

  1. Install myData as per Software Install and Update
  2. Update SQL Server to 2008R2 or newer
  3. Create Live and Training environments (Recommended naming of myData databases) Create a new myData configuration file (Global Configuration File Example)
    1. Restore database to each environment
 1 Day

 

 

myData 1.4 to myData 1.5

This upgrade takes 2 to 4 Days depending on size and scope of client data.

If integration using web services is being used clients should contact Assetic before proceeding as third party systems will also need to be upgraded

Task
Timing

Client supplies a zipped backup of the database

  1. myData is taken offline
  2. Client uploads myData database to Assetic's file server

1 Day

Close of business on the week prior to upgrade

Assetic upgrades client database to final 1.5 version of myData

  1. Upgrading 1.4
    1. Patching supplied 1.4 database to final 1.4 release
    2. Run the 1.4 archive upgrade utility
  2. Upgrading 1.5
    1. Run 1.4 to 1.5 upgrade utility
    2. Run the 1.5 admin utility

  3. myData 1.5 upgrades

    1. Migrate retired asset categories

      1. Footpaths to Pathways
      2. Kerbs and Pits to Kerbs
      3. Unsealed Roads to Roads

    2. Perform audit checks to ensure integrity has been maintained

      1. Asset Register
      2. Valuations
      3. SMP
    3. Generate a new user domain specific client licence file
    4. Apply licence file to database
 2-3 Days

Proceed to myData 1.5 to myData 1.6 (Assetic)

If Web Services integration is being used, clients should contact Assetic before proceeding as third party systems will also need to be upgraded

Assetic returns upgraded database to client

  1. Backup and zip database
  2. Include links for
    1. Current myData release
    2. Upgraded database with licence applied
    3. Relevant deployment guides
 1 Day

Client restores myData database

  1. Install myData as per Software Install and Update
  2. Update SQL Server to 2008R2 or newer
  3. Create Live and Training environments (Recommended naming of myData databases)
    1. Restore database to each environment
  4. Create a new myData configuration file (Global Configuration File Example)

 1 Day

 

myData 1.5 to myData 1.6 (Assetic)

This upgrade takes 1 Day, it can be performed by a client with a current software maintenance agreement

 

Task
Timing

Client supplies remote login details (Remote login configuration (Assetic assisted upgrade))

  1. myData is taken offline
  2. Database is backed up

Assetic upgrades client database to final 1.6 version of myData

  1. Upgrading 1.5 to 1.6
    1. Install myData 1.6
    2. Run the 1.6 admin utility
    3. Generate a new user domain specific client licence file including any GIS plugins
    4. Apply licence file to database
 2-3 Days

Assetic returns upgraded database to client

  1. Backup and zip database
  2. Include links for
    1. Current myData release
    2. Upgraded database with licence applied
    3. Relevant deployment guides
 1 Day

Client restores myData database

  1. Install myData as per Software Install and Update
  2. Update SQL Server to 2008R2 or newer
  3. Create Live and Training environments (Recommended naming of myData databases)
    1. Restore database to each environment
  4. Create a new myData configuration file (Global Configuration File Example)

 1 Day

 

myData 1.5 to myData 1.6 (Client)

This upgrade can be performed by a client with a current software maintenance agreement

If integration using web services is being used clients should contact Assetic before proceeding as third party systems will also need to be upgraded

Task Timing
Ensure myData has been upgraded to 1.5.11 before continuing
  1. Users should contact Assetic for
    1. the 1.6 installer
    2. a new licence file
 none
  1. Install myData as per Software Install and Update
  2. Update database as per Software Install and Update
  3. Apply licence file as per Applying / Updating a licence file

1 to 3 days

Clients should do this upgrade during AEDT/AEST working hours to ensure timely support is available

User needs to contact Assetic support for upgrades after version 1.6. For more information see the myData Version 1.7 Release Notes.

Remote login configuration (Assetic Managed Services Client)

  1. VPN connection
  2. Remote desktop login
    1. Required Programs on RD
      1. SQL Management Studio
      2. myData (current version)
      3. IIS Services Manager (for web services and Asset Cloud)
      4. SoapUI (Assetcloud)
    2. Optional Programs on RD (but preferred)
      1. Excel
      2. Notepad++
      3. qgis 2.0
  3. Other configuration
    1. RDP ideally should be into machine where Assetcloud is installed for assistance with mapping admin
    2. If Assetic are managing the upgrade of Assetcloud, myData and Web services the RDP user should have admin rights on the machine
    3. myData user called "Assetic" that is part of the myData Admin group